fix(ci): resolve beta release workflow failures #107
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e test The --benchmark-skip flag is not a valid pytest argument, causing 'error: unrecognized arguments' in beta-release workflow. Replaced with simple performance test that doesn't require pytest-benchmark plugin. Changes: - Remove invalid --benchmark-skip flag - Use simple_performance_test.py for performance validation - Maintains performance verification without plugin dependencies - Runs with optimal performance settings (4 threads, no memory debugging) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Since 4.2.0 has not been publicly released yet, creating 4.2.0b1 beta instead of jumping to 4.3.0b1. This allows proper beta testing of the current 4.2.0 feature set before the official release. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Improvements to beta-release workflow: 1. Fixed version logic: Create beta of current version (4.2.0b1) instead of auto-incrementing minor version (4.3.0b1) for unreleased versions 2. Updated token usage: Use GH_PAT instead of GITHUB_TOKEN to resolve permission issues with git operations 3. Better versioning strategy: - 4.2.0 (unreleased) → 4.2.0b1 (current approach) - 4.2.0b1 → 4.2.0b2 (future increments) - Only increment minor version after official release 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Improvements to beta-release workflow: 1. Fixed version logic: Create beta of current version (4.2.0b1) instead of auto-incrementing minor version (4.3.0b1) for unreleased versions 2. Updated token usage: Use GH_PAT instead of GITHUB_TOKEN to resolve permission issues with git operations 3. Better versioning strategy: - 4.2.0 (unreleased) → 4.2.0b1 (current approach) - 4.2.0b1 → 4.2.0b2 (future increments) - Only increment minor version after official release 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…og-python into fix/performance-regression
- Fetch all tags before determining next beta version - Loop through beta numbers to find next available version (e.g., b1 → b2 → b3) - Prevents 'tag already exists' errors when v4.2.0b1 exists - Ensures automatic increment to v4.2.0b2, v4.2.0b3, etc. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 CRITICAL BUG FIX
Beta workflow was accidentally publishing STABLE releases to PyPI instead of beta releases!
Root Cause Analysis
4.2.0b3v4.2.0b3(Pre-release)datafog-4.2.0(STABLE VERSION)Problem:
setup.pyhad hardcodedversion = '4.2.0'that overrode the beta version during package build.Fixes Applied
setup.py Version Management
datafog/__about__.pyWorkflow Cleanup
sedcommand forsetup.py__about__.py)Changelog Script Arguments
--betaand--outputflag supportopen BETA_CHANGELOG.md: no such file or directoryBeta Version Auto-Increment
git fetch --tagsfor complete tag historyv4.2.0b1→v4.2.0b2→v4.2.0b3Impact
4.2.0to PyPI (❌)4.2.0b4to PyPI (✅)Validation
✅ Local testing confirms
setup.pynow reads beta versions correctly✅ Version detection logic works: finds next available beta number
✅ Changelog generation works with
--beta --output BETA_CHANGELOG.mdThis is a critical fix to prevent accidental stable releases.